This PR was a feature, as it changed the default behavior. It's been released in 6.1.3.

@hansl what do you suggest we do? Cut a 6.1.4 that removes this change?

Actually probably the most semver option, yes. Revert it in the patch (6.1.4 is due today anyway) and leave it alone in master.

This isn't a feature but rather a fix for a regression. See #11195, #8148 and #8501.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}